Resource provider account token provisioning and processing

ABSTRACT

Embodiments are directed to issuing tokens for identifiers associated with a resource provider account specific to the resource provider issuing the account. A resource provider processor system interfaces with a resource provider computer to validate account eligibility upon receiving a token request message. If the account is eligible for token generation, the resource provider processor system generates a universal identifier corresponding to the identifier associated with the resource provider account and returns the universal identifier to the token requestor. The token requestor may send a token request message to a token issuer for obtaining a token using the universal identifier. Accordingly, the universal account identifier can be used to provision a token into a digital wallet. Transactions using the token may be processed with the resource provider processor system acting as an account issuer.

BACKGROUND

As digital wallets gain increasing popularity and wide spread use, users would like to provision various types of accounts on their digital wallets. For example, users may wish to provision resource provider accounts on their digital wallets. A resource provider account may be an account that is only valid at (e.g. can be used at) the resource provider that created the account. For example, a merchant-specific account is an example of a resource provider account.

However, resource provider accounts (e.g., gift card accounts, prepaid accounts, entity-specific accounts, etc.) are susceptible to being compromised and used fraudulently. This poses a security risk for the resource provider accounts. In addition, the resource provider accounts cannot currently be provisioned into digital wallets.

Embodiments of the present invention solve these problems and other problems, individually and collectively.

BRIEF SUMMARY

Embodiments of the present invention enable issuing a token for a resource provider account specific to (e.g. exclusively valid at) the resource provider issuing the account. A resource provider processor system interfaces with a resource provider computer to validate account eligibility for tokenization upon receiving a token request message from a token requestor. If the account is eligible for token generation (e.g. tokenization), the resource provider processor system generates a universal identifier corresponding to the identifier associated with the resource provider account and returns the universal identifier to the token requestor. The token requestor may send a token request message to a token issuer for obtaining a token using the universal identifier. Accordingly, the universal account identifier can be used to provision a token into a digital wallet. According to various embodiments, one or more limitations may be associated with the resource provider account (e.g. transaction limits or restrictions). In such embodiments, the limitations may be provided to the token issuer to be associated with the generated token. The token may be subject to the same limitations associated with the resource provider account.

Transactions using the token may be processed by the resource provider processor system acting as an account issuer. That is, when a transaction processing system receives a transaction request including the token, the transaction processing system may contact the resource provider processor that issued the universal identifier to process the transaction.

Embodiments provide a method including receiving, by a resource provider processor system, a token request message from a token requestor. The token request message includes a first identifier associated with a resource provider account. The resource provider processor system identifies a resource provider computer associated with the first identifier. The resource provider processor system validates the first identifier with the resource provider computer. In some embodiments, the resource provider processor system may determine that the resource provider account is eligible for tokenization. The resource provider processor system generates a universal identifier associated with the resource provider account, the universal identifier identifying the resource provider account and the resource provider processor system. In some embodiments, a format of the universal identifier is attributed to the resource provider processor system. A format of the first identifier included in the token request message may be different than the format of the universal identifier generated by the resource provider processor system. The method further includes transmitting, by the resource provider processor system, the universal identifier to the token requestor. The token requestor requests a token for the universal identifier from a token issuer server computer. In some embodiments, the token issuer server computer includes a universal account processor server computer. In some embodiments, a mapping between the universal identifier and the first identifier associated with the resource provider account may be stored at a token vault.

In some embodiments, the method may also include determining, by the resource provider processor system, one or more restrictions associated with the resource provider account; and transmitting, by the resource provider processor system, the one or more restrictions to the token issuer server computer such that the token generated by the token issuer server computer is associated with the one or more restrictions. According to various embodiments, the resource provider processor system may contact the resource provider computer to inactivate the first identifier associated with the resource provider account.

In some embodiments, the resource provider processor system may receive identification and verification data associated with account holder of the resource provider account. The resource provider processor system may verify an identity of the account holder using the identification and verification data.

Embodiments may also provide a system including a processor and a computer readable medium coupled to the processor. The computer readable medium comprises code, executable by the processor, to implement the above-described method.

Embodiments further provide a method including receiving, by a token issuer server computer, a token request message including a first identifier from a token requestor. The token issuer server computer determines that the first identifier is associated with a resource provider account. The token issuer server computer transmits a universal identifier request to a resource provider processor system. The universal identifier request includes the first identifier and requests a universal identifier corresponding to the first identifier. The token issuer server computer receives the universal identifier corresponding to the first identifier from the resource provider processor system. The method also includes generating, by the token issuer server computer, a token for the universal identifier. The token represents the universal identifier. The token issuer server computer stores a mapping between the token and the universal identifier at a token vault. The method further includes transmitting, by the token issuer server computer, the token to the token requestor.

In some embodiments, the token issuer server computer includes an universal account processing server computer. In such embodiments, the method further includes receiving, at the universal account processing server computer, a transaction request including the token. The universal account processing server computer retrieves the universal identifier represented by the token from the token vault. The universal account processing server modifies the transaction request to include the universal identifier represented by the token, and transmits the modified transaction request including the universal identifier to the resource provider processor system for processing.

In some embodiments, the token issuer server computer may receive one or more restrictions associated with the resource provider account. The token issuer server computer may store the one or more restrictions along with the generated token at the token vault such that the generated token is subject to the one or more restrictions. In embodiments where the token issuer server computer includes the universal account processing server computer, the universal account processing server computer may determine the one or more restrictions associated with the resource provider account. The universal account processing server computer may apply the restrictions to the resource provider account.

These and other embodiments are described in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram including a token generation system for resource provider account(s) in accordance with embodiments of the present application.

FIG. 2 shows a block diagram of a system for processing a transaction using a token associated with a resource provider account in accordance with embodiments of the present application.

FIG. 3 shows a block diagram of an exemplary resource provider processor system in accordance with some embodiments of the invention.

FIG. 4 illustrates a system and a flow diagram for generating a token associated with a resource provider account in accordance with some embodiments of the invention.

FIG. 5 illustrates another system and a flow diagram for generating a token associated with a resource provider account in accordance with some embodiments of the invention.

FIG. 6 shows an exemplary computer system according to embodiments of the present invention.

DETAILED DESCRIPTION

Embodiments are directed to methods, apparatuses, computer readable media and systems for issuing tokens for identifiers associated with a resource provider-specific account. The resource provider account may be exclusively valid at the resource provider that issued the account. For example, a resource provider account may be a closed-loop account, e.g. a retail store account. Upon receiving a token request message from a token requestor, a resource provider processor system interfaces with a resource provider computer to validate account eligibility for tokenization. If the account is eligible for token generation (e.g. tokenization), the resource provider processor system generates a universal identifier corresponding to the identifier associated with the resource provider account and returns the universal identifier to the token requestor. The token requestor may send a token request message to a token issuer system for obtaining a token using the universal identifier. Accordingly, the universal account identifier can be used to provision a resource provider account into a digital wallet. Transactions using the token may be processed with the resource provider processor system acting as an account issuer. That is, when a transaction processing system receives a transaction request including the token, the transaction processing system may contact the resource provider processor that issued the universal identifier to process the transaction.

According to various embodiments, one or more limitations (e.g. transaction limits or restrictions) may be associated with the resource provider account. In such embodiments, the limitations may be provided to the token issuer to be associated with the generated token. The token may be subject to the same limitations associated with the resource provider account.

In an exemplary embodiment, the resource provider may be a merchant. Accordingly, the resource provider account may be a user account at the merchant. Multiple merchants may work with a processing system (e.g. the resource provider processor system) to process transactions using the merchant accounts. When the user wishes to provision the user's merchant account onto the user's mobile device, the user needs to provide a valid account identifier (e.g. a universal identifier) to a token issuer system. Conventionally, tokens are not issued for merchant-specific accounts, e.g. closed-loop accounts. Thus, the user needs to obtain a valid account identifier (e.g. a universal identifier, an open-loop account identifier) associated with the user's merchant account.

The user may contact the processing system to request a token for the user's merchant account. For example, the user may send a token request message including an account identifier identifying the user's merchant account to the processing system. The processing system may identify the specific merchant based on the format of the account identifier provided in the token request message. The processing system may contact the merchant to ensure that the user's merchant account is eligible for tokenization (e.g. token generation). Upon confirming eligibility, the processing system may generate a universal identifier for the user's merchant account. A format of the universal identifier may indicate that the universal identifier is generated by the processing system as opposed to issuers that conventionally generate the universal identifiers. The processing system may return the universal identifier to the user or may contact a token issuer system to request a token with the universal identifier. If the processing system receives the token from a token issuer on behalf of the user, the processing system provides the token to the user. The user's merchant account may then be provisioned on the user's digital wallet.

Continuing with the foregoing exemplary embodiment, at a later time, the user initiates a transaction using the token associated with the merchant account. When the transaction is initiated using the user's digital wallet, a transaction request message including the token may be sent to a transaction processing system. The transaction processing system may process the transaction request message and identify that the token is associated with a merchant account. The transaction processing system may also identify that the universal account identifier represented by the token is issued by the resource provider processor system. Accordingly, the resource provider processor system may act as an account issuer for the purposes of this transaction. The transaction processing system may interact with the resource provider processor system to process the transaction request initiated using the token.

Before discussing specific embodiments and examples, some descriptions of terms used herein are provided below.

As used herein, a “user device” may comprise any suitable electronic device that may be transported and/or operated by a user, which may also provide remote communication capabilities to a network. Examples of remote communication capabilities include using a mobile phone (wireless) network, wireless data network (e.g. 3G, 4G or similar networks), Wi-Fi, Wi-Max, or any other communication medium that may provide access to a network such as the Internet or a private network. Examples of user devices include mobile phones (e.g. cellular phones), PDAs, tablet computers, net books, laptop computers, personal music players, hand-held specialized readers, game consoles, etc. Further examples of user devices may also include wearable devices, such as smart watches, fitness bands, ankle bracelets, rings, earrings, etc., as well as automobiles with remote communication capabilities. A user device may comprise any suitable hardware and software for performing such functions, and may also include multiple devices or components (e.g. when a device has remote access to a network by tethering to another device—i.e. using the other device as a modem—both devices taken together may be considered a single mobile device).

A “server computer” may typically be a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit.

A “user” may include an individual or an entity that uses a system. A user may be associated with one or more accounts and/or user devices. In some cases, the user may also be referred to as an account holder, or consumer.

A “wallet” may refer to a digital wallet or an e-wallet which is a software application that allows an individual to conduct electronic commerce transactions. A digital wallet may store payment credentials, bank account information, one or more digital wallet identifiers and/or the like and can be used in a variety of transactions, such as but not limited to eCommerce, social networks, money transfer/personal payments, mobile commerce, proximity payments, and/or the like for retail purchases, digital goods purchases, utility payments, transferring funds between users, and/or the like. A digital wallet may be designed to streamline the purchase and payment process. A digital wallet may also store transaction records (e.g., electronic receipts).

A “credential” may be any suitable information that serves as reliable evidence of worth, ownership, identity, or authority. A credential may be a string of numbers, letters, or any other suitable characters that may be present or contained in any object or document that can serve as confirmation.

A “resource provider” may be an entity that can provide a resource such as goods, services, information, and/or access. Examples of a resource provider includes merchants, access devices, secure data access points, etc. A merchant may typically be an entity that engages in transactions and can sell goods or services, or provide access to goods or services.

“Account identifier” or “identifier” may include any suitable information associated with an account (e.g. a payment account, a resource access account, etc. and/or a device associated with the account). Such information may be directly related to the account or may be derived from information related to the account. Examples of account information may include an account number (e.g. a primary account number (PAN)), user name, expiration date, CVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification values, etc. CVV2 is generally understood to be a static verification value associated with a payment device. CVV2 values are generally visible to a user (e.g., a consumer), whereas CVV and dCVV values are typically embedded in memory or authorization request messages and are not readily known to the user (although they are known to the issuer and payment processors). Account identifiers may include resource provider specific account identifiers or universal identifiers. A resource provider specific account identifier may identify an account issued by a resource provider computer. A universal identifier may identify an account issued by account issuers (e.g. open loop issuers). A universal identifier may have a different format than a resource provider specific account identifier. An issuer of the account may be identified by analyzing the format of the account identifier. In some embodiments, a universal identifier associated with a resource provider specific account may be generated by a resource provider processor system. In such embodiments, the resource provider processor system may act as the issuer for the generated universal identifier.

A “digital wallet” can include an electronic device that allows an individual to conduct electronic commerce transactions. A digital wallet may store user profile information, account credentials, one or more digital wallet identifiers and/or the like and can be used in a variety of transactions, such as but not limited to eCommerce, social networks, money transfer/personal payments, mobile commerce, proximity payments, access transactions, and/or the like. A digital wallet may be designed to streamline the transaction process. A digital wallet may allow the user to load one or more account identifiers onto the digital wallet so as to conduct a transaction without having to enter an account identifier or present a physical identification.

A “digital wallet provider” may include an entity, such as an issuing entity or third party service provider, that issues a digital wallet to a user that enables the user to conduct transactions. A digital wallet provider may provide standalone user-facing software applications that store account numbers, or representations of the account numbers (e.g., tokens), on behalf of an account holder (or other user) to facilitate transactions at more than one unrelated transacting entity, perform person-to-person transactions, or load value into the digital wallet. A digital wallet provider may enable a user to access its account via a personal computer, mobile device or access device.

A “token” may be a substitute value for a credential. A token may be a string of numbers, letters, or any other suitable characters. Examples of tokens include payment tokens, access tokens, personal identification tokens, etc. For example, a payment token may include an identifier for a payment account that is a substitute for an account identifier, such as a primary account number (PAN). For example, a token may include a series of alphanumeric characters that may be used as a substitute for an original account identifier. For example, a token “4900 0000 0000 0001” may be used in place of a PAN “4147 0900 0000 1234.” In some embodiments, a token may be “format preserving” and may have a numeric format that conforms to the account identifiers used in existing transaction processing networks (e.g., ISO 8583 financial transaction message format). In some embodiments, a token may be used in place of a PAN to initiate, authorize, settle or resolve a transaction or represent the original credential in other systems where the original credential would typically be provided. In some embodiments, a token value may be generated such that the recovery of the original PAN or other account identifier from the token value may not be computationally derived. Further, in some embodiments, the token format may be configured to allow the entity receiving the token to identify it as a token and recognize the entity that issued the token.

A “token provider” or “token service system” can include a system that that services tokens. In some embodiments, a token service system can facilitate requesting, determining (e.g., generating) and/or issuing tokens, as well as maintaining an established mapping of tokens to primary account numbers (PANs) in a repository (e.g. token vault). In some embodiments, the token service system may establish a token assurance level for a given token to indicate the confidence level of the token to PAN binding. The token service system may include or be in communication with a token vault where the generated tokens are stored. The token service system may support token processing of transactions submitted using tokens by de-tokenizing the token to obtain the actual PAN. In some embodiments, a token service system may include a tokenization computer alone, or in combination with other computers such as a transaction processing system.

A “token request message” may be an electronic message for requesting a token. A token request message may include information usable for identifying an account or digital wallet, and/or information for generating a token. For example, a token request message may include credentials, mobile device identification information (e.g. a phone number or MSISDN), a digital wallet identifier, information identifying a tokenization service provider, a merchant identifier, a cryptogram, and/or any other suitable information. Information included in a token request message can be encrypted (e.g., with an issuer-specific key). In some embodiments, a token request message may be formatted as an authorization request message (e.g., an ISO 8583 message format). In some embodiments, the token request message may include a flag or other indicator specifying that the message is a token request message.

A “token response message” may be a message that responds to a token request. A token response message may include an indication that a token request was approved or denied. A token response message may also include a token, mobile device identification information (e.g. a phone number or MSISDN), a digital wallet identifier, information identifying a tokenization service provider, a merchant identifier, a cryptogram, and/or any other suitable information. Information included in a token response message can be encrypted (e.g., with an issuer-specific key). In some embodiments, a token response message may be formatted as an authorization response message (e.g., an ISO 8583 message format). In some embodiments, the token response message may include a flag or other indicator specifying that the message is a token response message.

An “acquirer” may typically be a business entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities can perform both issuer and acquirer functions. Some embodiments may encompass such single entity issuer-acquirers. An acquirer may operate an acquirer computer, which can also be generically referred to as a “transport computer”.

An “authorizing entity” may be an entity that authorizes a request. Examples of an authorizing entity may be an issuer, a governmental agency, a document repository, an access administrator, etc. An “issuer” may typically refer to a business entity (e.g., a bank) that maintains an account for a user. An issuer may also issue credentials stored on a user device, such as a cellular telephone, smart card, tablet, or laptop to the consumer.

An “authorization request message” may be an electronic message that requests authorization for a transaction. In some embodiments, it is sent to a transaction processing computer and/or an issuer of an account to request authorization for a transaction. An authorization request message according to some embodiments may comply with ISO 8583, which is a standard for systems that exchange electronic transaction information associated with a payment made by a user using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with an account. An authorization request message may also comprise additional data elements corresponding to “identification information” including, by way of example only: a service code, a CVV (card verification value), a dCVV (dynamic card verification value), an account number, a token, a user name, an expiration date, etc. An authorization request message may also comprise “transaction information,” such as any information associated with a current transaction, such as the transaction amount, transacting entity identifier, transacting entity location, acquirer bank identification number (BIN), card acceptor ID, information identifying items being purchased, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction.

An “authorization response message” may be a message that responds to an authorization request. In some cases, it may be an electronic message reply to an authorization request message generated by an account issuing institution or a transaction processing computer. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—transaction was approved; Decline—transaction was not approved; or Call Center—response pending more information. The authorization response message may also include an authorization code, which may be a code that an account issuing entity returns in response to an authorization request message in an electronic message (either directly or through the transaction processing computer) to the transacting entity that indicates approval of the transaction. The code may serve as proof of authorization. As noted above, in some embodiments, a transaction processing computer may generate or forward the authorization response message to the transacting entity.

Embodiments enable provisioning a resource provider account on a digital wallet. When the user of the resource provider account wishes to provision the resource provider account on the digital wallet, the digital wallet may send an account identifier to a resource provider processor system to request the provisioning of the account on the digital wallet. The resource provider processor system may analyze the account identifier and identify the resource provider that issued the resource provider account. The resource provider processor system may send a status request message to the resource provider computer to ensure that the resource provider account is eligible for tokenization and/or for being provisioned on user's digital wallet. Based on the response received from the resource provider computer, the resource provider processor system may generate a universal account identifier for the resource provider account. That is, the resource provider processor system may become an issuer or act as a proxy issuer for the universal account identifier. In some embodiments, the resource provider processor system may send the universal account identifier to the user. The user may then request a token from a token issuer computer using the universal account identifier. Alternatively, the resource provider processor system may contact the token issuer computer to request the token for the universal account identifier and may return the token to the user.

FIG. 1 shows a block diagram including a token generation system 100 for resource provider account(s) in accordance with embodiments of the present application. The token generation system includes a resource provider processor system 125, a token issuer computer 140 in communication with a token vault 150, and a resource provider computer 130.

The resource provider processor system 125 may be an entity that processes transactions using account(s) issued by the resource provider(s) computer 130. In some embodiments, the accounts issued by the resource provider computer 130 may be “closed-loop” accounts. A closed-loop account may only be used with the resource provider of that account. For example, an account generated by a specific merchant or service provider may be a closed-loop account where the user may conduct transactions using the account only with the merchant or the service provider.

One or more users 110, 120 may be in communication with the resource provider processor system 125 to request the provisioning of their resource provider account(s) 112, 114, 122, 124 on their user devices. For example, the resource provider processor system 125 may receive an account provisioning request message or a token request message from the user 110 or 120. The account provisioning request message or a token request message may include an account identifier identifying a resource provider account 112, 114 of the user 110 (and/or resource provider account 122, 124 of the user 120).

In some embodiments, the resource provider processor system 125 may also receive identification and verification data from the user 110 or 120. The identification and verification data may be associated with account holder of the resource provider account (e.g. user 110 or 120). The resource provider processor system 125 may verify an identity of the user 110 or 120 using the identification and verification data.

Upon receiving the provisioning request message or a token request message, the resource provider processor system 125 may identify the resource provider computer 130 that issued the resource provider account. The resource provider processor system 125 may contact the resource provider computer 130 to request the status of the resource provider account. For example, if the account is a payment account, the resource provider processor system 125 may request the balance on the payment account. Alternatively, if the account is an access account, the resource provider processor system 125 may ensure that the account is still active or belongs to an active user of the account. Based on the status of the resource provider account, the resource provider processor system 125 may determine that the resource provider account is eligible for tokenization. The resource provider processor system 125 may then generate a universal account identifier identifying the resource provider account.

A universal account identifier may have a different format than the account identifier generated by the resource provider computer 130. For example, the universal account identifier may be globally recognized. An exemplary universal account identifier may be a 16-digit primary account number (PAN) such as 4147 0900 0000 1234. The universal account identifier may be used for processing transactions by entities other than the resource provider computer 130.

In some embodiments, the resource provider processor system 125 may send a token request message including the universal account identifier to the token issuer computer 140. The token issuer computer 140 may generate a token corresponding to the universal account identifier associated with the resource provider account of the user. The token issuer computer 140 may store a mapping between the token and the universal account identifier in the token vault 150. The token issuer computer 140 may return the token to the resource provider processor system 125. The resource provider processor system 125 may send the token to the user device of the user 110, 120.

In other embodiments, the resource provider processor system 125 may send the universal account identifier to the user 110, 120. The user 110, 120 may then send the provisioning request message or the token request message including the universal account identifier to the token issuer computer 140. The token issuer computer 140 may generate a token corresponding to the universal account identifier associated with the resource provider account 112, 114 of the user 110 (or resource provider account 122, 124 of the user 120). The token issuer computer 140 may store a mapping between the token and the universal account identifier in the token vault 150. The token issuer computer 140 may return the token to the user device of the user 110, 120.

When the token is returned to the user device, the resource provider account may be provisioned on the user device. The user may then initiate a transaction using the token. FIG. 2 shows a block diagram of a system 200 for processing a transaction using a token associated with a resource provider account in accordance with embodiments of the present application. The system 200 includes a user 110, a transacting entity computer 210, an acquirer computer 220, a universal account processor system 230, a resource provider processor system 125, and a token vault 150. An acquirer may operate the acquirer computer 220. An “acquirer” is typically a business entity that has a business relationship with a particular merchant or other entity.

The system 200 comprises a user 110 who may operate a user device. The user 110 may use the user device to conduct a transaction (e.g., a payment transaction) at a transacting entity computer 210. The transacting entity computer 210 may be connected to an acquirer computer 220. The acquirer computer 220 may be connected to the resource provider processor system 125 via the universal account processor system 230. Of course, some or all of these entities depicted as connected may be connected across one or more communication networks or may be directly connected.

A “transacting entity” may typically be an entity that engages in transactions and may sell goods and/or services. A “resource provider” may typically refer to a business entity (e.g., a bank, a merchant, an online portal, an employer, an access control system, etc.) that maintains accounts for users and may issue credentials to be stored on the user device (e.g., a cellular telephone, smart card, tablet, laptop, wearable computing devices, etc.) of the user 110. The user device may interact with the transacting entity computer 210 (e.g., via the Internet to access a website or utilize an application provided by transacting entity computer 210) to initiate and/or conduct a transaction. Each of the entities (e.g., transacting entity computer 210, acquirer computer 220, universal account processor system 230, resource provider processor system 125, and token vault 150) may comprise one or more computer apparatuses to enable communications or to perform one or more of the functions described herein.

The universal account processor system 230 may include data processing subsystems, networks, and operations used to support and deliver certificate authority services, authorization services, exception file services, and clearing and settlement services. An exemplary universal account processor system 230 may include a payment processing network such as VisaNet™. VisaNet™, in particular, includes a VIP system (Visa Integrated Payments system) that processes authorization requests and a Base II system that performs clearing and settlement services. In some embodiments, the universal account processor system 230 may conduct transactions in substantially real-time (e.g., in fewer than a few seconds or fractions of a second). The universal account processor system 230 may include one or more server computers (as described above). The universal account processor system 230 may use any suitable wired or wireless network, including the Internet. In some embodiments, the universal account processor system 230 may be the same as or may be associated with a token issuer system.

In an exemplary purchase transaction, the user 110 purchases a good or service at from a transacting entity using a user device (e.g., a mobile phone). The user device can interact with the transacting entity computer 210. For example, the user 110 may tap the user device against an NFC reader coupled to the transacting entity computer 210 to present the token stored on the user device to the transacting entity computer 210 (step 1). Alternatively, the user 110 may provide credentials to the transacting entity electronically, such using a digital wallet or in through an online transaction.

To cause the transaction to be performed, an authorization request message is generated by the transacting entity computer 210 and is forwarded to the acquirer computer 220 (step 2). Such an “authorization request message” may be an electronic message that is sent to a universal account processor system 230 and/or an resource provider processor system 125 of an account used in the transaction to request authorization for the transaction. An authorization request message, according to some embodiments, may comply with a message type defined by the International Organization for Standardization (ISO) 8583 standard, which is a standard for systems that exchange electronic transaction information associated with payments made by users using a payment account. The authorization request message may include the token provided by the user 110 to the transacting entity computer 210. An authorization request message may also comprise additional data elements corresponding to “identification information” including, by way of example only: a service code, a CVV (card verification value), a dCVV (dynamic card verification value), an expiration date, etc. An authorization request message may also include “transaction information,” such as any information associated with a current transaction, such as the transaction amount, transacting entity identifier, transacting entity location, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction.

After receiving the authorization request message, the acquirer computer 220 will send the authorization request message to the universal account processor system 230 (step 3). The universal account processor system 230 may recognize that the authorization request message includes a token. The universal account processor system 230 may send the token to the token vault 150 for de-tokenization, e.g. to receive a universal account identifier corresponding to the token (step 4). Upon receiving the universal account identifier (e.g. a 16-digit PAN) represented by the token, the universal account processor system 230 may recognize that the universal account identifier is generated by the resource provider processor system 125. For example, the universal account processor system 230 may identify the resource provider processor system 125 based on a format of the universal account identifier, e.g. the universal account identifier may include a symbol or alphanumerical character that is associated with or indicative of the resource provider processor system 125. For example, the universal account identifier may be a 16-digit PAN such as 4147 0900 0000 1234. The first four digits 4147 may identify a specific resource provider processor system 125 that issued this specific PAN.

Upon receiving the universal account identifier from the token vault 150, the universal account processor system 230 may modify the authorization request message to include the universal account number (in addition to or in lieu of the token) and forward the authorization request message to the resource provider processor system 125 (step 5). The universal account number received from the token vault 150 may be used by the universal account processor system 230 to identify the appropriate resource provider processor system 125 for the purpose routing or processing (e.g., determining a risk of the authorization request, which may be based upon known rules of the involved resource provider) the message.

After the resource provider processor system 125 receives the authorization request message, the resource provider processor system 125 sends an authorization response message back to the universal account processor system 230 to indicate whether or not the current transaction is authorized (step 6). An “authorization response message” may be an electronic message reply to an authorization request message generated by the universal account processor system and may comply with the ISO 8583 standard. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—transaction was approved; Decline—transaction was not approved; or Call Center—response pending more information.

The universal account processor system 230 receives the authorization response message from the resource provider processor system 125 and transmits the authorization response message back to the acquirer computer 220. The acquirer computer 220 then sends the authorization response message back to the transacting entity computer 210, where the transacting entity can determine whether to proceed with the transaction.

If the transaction is a financial transaction, a normal clearing and settlement process can be conducted by the universal account processor system 230 at the end of the day. A clearing process is a process of exchanging financial details between an acquirer and an issuer to facilitate posting to a user's payment account and reconciliation of the user's settlement position. However, it should be noted that embodiments of the invention are not limited to a single settlement process.

FIG. 3 shows a block diagram of a resource provider processor system 125 in accordance with embodiments of the present application. The resource provider processor system 125 comprises a processor 314, a memory or storage 312, an external communication interface 310 (e.g. a network interface), and a computer readable medium 302.

The computer readable medium 302 may comprise an analysis module 304, a validation module 306, an account identifier generation module 308, and any other suitable software module(s). The computer readable medium 201 may also comprise code, executable by the processor 314 for implementing a method comprising receiving a token request message from a token requestor, where the token request message includes a first identifier associated with a resource provider account. The method also includes identifying a resource provider computer associated with the first identifier, and validating the first identifier with the resource provider computer. The method further comprises generating a universal identifier associated with the resource provider account, the universal identifier identifying the resource provider account and the resource provider processor system, and transmitting the universal identifier to the token requestor, where the token requestor requests a token for the universal identifier from a token issuer server computer.

The resource provider processor system 125 receives a token request message or a provisioning request message from a user via the external communication interface 310. The message includes an account identifier associated with a resource provider account issued by a resource provider. The analysis module 304 may comprise code that causes the processor 314 to analyze the received account identifier to identify the resource provider that issued (e.g. created) the account identifier and/or the resource provider account identified by the account identifier. In some embodiments, the analysis module 304 may determine the resource provider based on a format of the account identifier. For example, the analysis module 304 may determine that the account identifier is associated with a given resource provider computer if the account identifier starts with (or ends with, contains at a predetermined location, etc.) a specific character.

Upon identifying the resource provider associated with the account identifier, the validation module 306 may send a message to the resource provider computer via the external communication interface 310 to determine whether the resource provider account identified by the account identifier is eligible for tokenization and/or provisioning. In some embodiments, the validation module 306 may determine whether the resource provider account is eligible for tokenization. For example, the resource provider account may be a prepaid account storing value. The validation module 306 may ensure that the account has a positive balance to determine that the account is eligible for tokenization and/or provisioning.

In some embodiments, the token request message or a provisioning request message received from the user may include user identification and verification data such as user name, address, a passcode, etc. The validation module 306 may validate that the user sending the token request message is the authorized user of the resource provider account identified in the token request message.

When the validation module 306 determines that the resource provider account is a valid account, the validation module 306 may inform the account identifier generation module 308. The account identifier generation module 308 may generate a universal account identifier for the resource provider account. The universal account identifier may identify the resource provider account and may replace the account identifier provided by the user in the token request message or the provisioning request message.

The universal account identifier may have a format that is different than a format of the account identifier provided by the user. In some embodiments, the format of the universal account identifier may be recognized and processed by universal transaction processing entities other than the resource provider that issued the resource provider account. The format of the universal account identifier may identify the resource provider that issued the resource provider account identified by the universal account identifier. The format of the universal account identifier may also identify the resource provider processor system 125 as the issuer of the universal account identifier. For example, the universal account identifier may start with (or end with, include at a predetermined location, etc.) a symbol or an alphanumerical character (e.g. an indicator) that is associated with the resource provider and/or the resource provider processor system 125. Accordingly, when the universal account identifier is analyzed and/or processed by a universal transaction processing entity, the universal transaction processing entity may identify the resource provider processor system 125 as the issuer of the universal account identifier.

According to various embodiments, the account identifier generation module 308 may generate additional information associated with the resource provider account. For example, the account identifier generation module 308 may generate a validation code, an expiration date, etc. associated with the resource provider account.

In some embodiments, upon generating the universal account identifier, the resource provider processor system 125 may send an account closure request to the resource provider computer via the external communication interface 310. The account closure request may inactivate the account identifier initially provided to the resource provider processor system 125 by the user.

FIGS. 4 and 5 illustrate methods for generating a token associated with a resource provider account and returning the token to the user according to embodiments of the invention. The steps shown in any method herein may be performed sequentially or in any suitable order in embodiments of the invention. In some embodiments, one or more of the steps may be optional. The various messages described below may use any suitable form of communication. In some embodiments, a request or response may be in an electronic message format, such as an e-mail, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, a hypertext transfer protocol (HTTP) request message, a transmission control protocol (TCP) packet, a web form submission. The request or response may be directed to any suitable location, such as an e-mail address, a telephone number, an internet protocol (IP) address, or a uniform resource locator (URL). In some embodiments, a request or response may comprise a mix of different message types, such as both email and SMS messages.

Referring now to FIG. 4, at S402, the user 110 may send a token request message or an account provisioning request message to the resource provider processing system 125 requesting a token for a resource provider account of the user 110. The token request message or the account provisioning request message may include an account identifier identifying the resource provider account of the user. The account identifier included in the request message may have a format.

At S404, the resource provider processing system 125 may analyze the account identifier and identify the resource provider that issued the resource provider account of the user. For example, the resource provider processing system 125 may identify the resource provider based on the format of the account identifier. In some embodiments, the account identifier may include an indicator identifying the resource provider that issued the resource provider account.

At S406, the resource provider processing system 125 may contact the resource provider computer 130 (e.g. a system of the identified resource provider) to request the status of the resource provider account. At S408, the resource provider processing system 125 may receive a response from the resource provider computer 130 regarding the status of the resource provider account.

At S410, the resource provider processing system 125 may determine whether the resource provider account eligible for token generation and/or provisioning on a user device based on the status of the resource provider account. For example, the resource provider account may be an account that stores value. If there is positive balance on the resource provider account, the account may be deemed to be active or to have favorable status (e.g. account is eligible for tokenization or for provisioning on a user device).

In some embodiments, at S410, the resource provider processing system 125 may request the resource provider computer 130 to close the resource provider account or deactivate the account identifier associated with the resource provider account when the resource provider account is deemed eligible for being provisioned on the user device.

At S412, the resource provider processing system 125 may generate a universal account identifier identifying the resource provider account. The universal account identifier may replace the account identifier provided to the resource provider processing system 125 by the user 110 at S402. The universal account identifier may be recognized and processed by universal transaction processing entities other than the resource provider who issued the resource provider account. The universal account identifier has a format, different from the format of the account identifier provided at S402, that is recognized by entities such as universal transaction processing entities or token issuing entities. The universal account identifier format may include a first indicator identifying the resource provider processing system 125 as the issuer of the universal account identifier. The universal account identifier format may also include a second indicator identifying the resource provider as the issuer of the resource provider account. For example, the universal account identifier may be a 16-digit PAN such as 4147 0900 0000 1234. The first four digits 4147 may identify a specific resource provider processor system 125 that issued this specific PAN. The next four digits 0900 may identify a specific source provider as the issuer of this PAN. This way, the universal transaction processing entity or token issuing entity may determine that the universal account identifier is associated with a resource provider account which would not be eligible for tokenization and/or provisioning without the universal account identifier.

At S414, the resource provider processing system 125 may send the universal account identifier to the user 110. The user 110 may request the resource provider account to be provisioned on their user device using the universal account identifier.

At S416, the user 110 may send a token request or a resource account provisioning request to a token issuer computer 140. The token issuer computer 140 may determine that the universal account identifier is associated with a resource provider account based on the format of the universal account identifier. However, since the format of the universal account identifier is recognizable (e.g. eligible for parsing) by the token issuer computer 140, the token issuer computer 140 may determine that a token can be generated for the universal account identifier.

At S418, the token issuer computer 140 may generate a token for the universal account identifier. At S420, the token issuer computer 140 may store the token and a mapping between the token and the universal account identifier at a token vault 150. At S422, the token issuer computer 140 may provide the token to the user 110. The token can be used to provision the resource provider account on the user device of the user 110.

In some embodiments, the resource provider processing system 125 may also receive, from the resource provider computer 130, restrictions associated with the resource account. In some embodiments, the restrictions may be applied by the user, the resource provider, the resource provider processor, the token issuer or the universal account processor system. For example, the resource account may be associated with access restrictions, spending restrictions, location-based restrictions, use-base restrictions, etc. The resource provider processing system 125 may provide (e.g. transmit) the restrictions associated with the resource provider account to the user 110 along with the universal account identifier. Such restrictions are passed (e.g. transmitted) to the token issuer computer 140 so that the generated token is associated with same or similar restrictions.

In some embodiments, at S414, instead of providing the universal account identifier to the user 110, the resource provider processing system 125 may send the universal account identifier directly to the token issuer computer 140 in a token request message. The token issuer computer 140 may generate the token and send it to the user 110 as described above in connection with S418-S422. In some embodiments, the token issuer computer 140 may send the token to the user via the resource provider processing system 125. Once the resource provider account is provisioned on the user device (e.g. on a digital wallet stored on the user device), the user 110 may conduct transactions with the resource provider account using the user device.

Referring now to FIG. 5, another method for generating a token associated with a resource provider account and returning the token to the user is described next. At S502, the user 110 may send a token request message or an account provisioning request message to the token issuer computer 140 requesting a token for a resource provider account of the user 110. The token request message or the account provisioning request message may include an account identifier identifying the resource provider account of the user. The account identifier included in the request message may have a format.

At S504, the token issuer computer 140 may analyze the account identifier and determine that the account identifier is associated with a resource provider account that is not eligible for token generation. In some embodiments, the token issuer computer 140 may determine that the account identifier is associated with a resource provider account based on the format of the account identifier.

At S506, the token issuer computer 140 may contact the resource provider processing system 125 and request a universal account identifier for the resource provider account associated with the account identifier received from the user 110 at S502. The universal account identifier request message sent from the token issuer computer 140 to the resource provider processing system 125 may include the account identifier provided to the token issuer computer 140 by the user 110 at S502.

At S508, the resource provider processing system 125 may analyze the account identifier and identify the resource provider that issued the resource provider account of the user. For example, the resource provider processing system 125 may identify the resource provider based on the format of the account identifier. In some embodiments, the account identifier may include an indicator identifying the resource provider that issued the resource provider account.

At S510, the resource provider processing system 125 may contact the resource provider computer 130 (e.g. a system of the identified resource provider) to request the status of the resource provider account. At S512, the resource provider processing system 125 may receive a response from the resource provider computer 130 regarding the status of the resource provider account.

At S514, the resource provider processing system 125 may determine whether the resource provider account eligible for token generation and/or provisioning on a user device based on the status of the resource provider account. For example, the resource provider account may be an account that stores value. If there is positive balance on the resource provider account, the account may be deemed to be active or to have favorable status (e.g. account is eligible for tokenization or for provisioning on a user device).

In some embodiments, at S516, the resource provider processing system 125 may request the resource provider computer 130 to close the resource provider account or deactivate the account identifier associated with the resource provider account when the resource provider account is deemed eligible for being provisioned on the user device. That is, once the account is deemed to be eligible for provisioning and a token is provisioned for that account, the actual account number can no longer be used because it is being replaced by the token.

At S518, the resource provider processing system 125 may generate a universal account identifier identifying the resource provider account. The universal account identifier may replace the account identifier provided to the resource provider processing system 125 by the token issuer computer 140 at S506. The universal account identifier may be recognized and processed by universal transaction processing entities other than the resource provider who issued the resource provider account. The universal account identifier has a format, different from the format of the account identifier provided to the resource provider processing system 125 at S506, that is recognized by entities such as universal transaction processing entities or token issuing entities. The universal account identifier format may include a first indicator identifying the resource provider processing system 125 as the issuer of the universal account identifier. The universal account identifier format may also include a second indicator identifying the resource provider as the issuer of the resource provider account. This way, the universal transaction processing entity or token issuing entity may determine that the universal account identifier is associated with a resource provider account which would not be eligible for tokenization and/or provisioning without the universal account identifier.

At S520, the resource provider processing system 125 may send the universal account identifier to the token issuer computer 140. At S522, the token issuer computer 140 may generate a token for the universal account identifier. At S524, the token issuer computer 140 may store the token and a mapping between the token and the universal account identifier at a token vault 150. At S526, the token issuer computer 140 may provide the token to the user 110. The token can be used to provision the resource provider account on the user device of the user 110. Once the resource provider account is provisioned on the user device (e.g. on a digital wallet stored on the user device), the user 110 may conduct transactions with the resource provider account using the user device.

In some embodiments, the resource provider processing system 125 may also receive, from the resource provider computer 130, restrictions associated with the resource account. In some embodiments, the restrictions may be applied by the user, the resource provider, the resource provider processor, the token issuer or the universal account processor system. For example, the resource account may be associated with access restrictions, spending restrictions, location-based restrictions, use-base restrictions, etc. In embodiments, where the user determines the restrictions, the user may select or create the restrictions (e.g. different spending restrictions) via a graphical user interface (GUI) on a user device (e.g. user computer, user mobile device, etc.). The resource provider processing system 125 may provide (e.g. transmit) the restrictions associated with the resource provider account to the token issuer computer 140 along with the universal account identifier. The token generated by the token issuer computer 140 is subject to (e.g. is associated with) the same or similar restrictions.

Embodiments of the invention have a number of advantages. For example, in embodiments of the invention, non-universal accounts, such as resource provider specific accounts, can be provisioned into user devices (e.g. into digital wallets) by creating a universal account identifier for a non-universal account. In connection with the provisioning, embodiments enable token generation for the non-universal accounts, such as resource provider specific accounts. Accordingly, users may not need to store or carry different identification proof for various non-universal accounts, and all account identifiers may be stored and/or provisioned on user's mobile device, for example on a digital wallet.

Embodiments further allow for the system to be replicated for many closed-loop systems. Specifically, systems 100 and 200 may be used in connection with any resource provider and/or resource provider processor.

Embodiments further allow a universal transaction processing entity to be able to process transactions initiated with resource provider accounts which are not traditionally eligible for processing by the universal transaction processing entity.

The various participants and elements shown in FIGS. 1-5 may operate one or more computer apparatuses (e.g., a server computer) to facilitate the functions described herein. Any of the elements in FIGS. 1-5 may use any suitable number of subsystems to facilitate the functions described herein. Examples of such subsystems or components are shown in FIG. 6. The subsystems such as a printer 608, keyboard 614, fixed disk 616 (or other memory comprising computer readable media), monitor 620, which is coupled to a display adapter 610, and others are shown. Peripherals and input/output (I/O) devices, which couple to I/O controller 602, can be connected to the computer system by any number of means known in the art, such as serial port 612. For example, serial port 612 or external interface 618 can be used to connect the computer apparatus to a wide area processing server computer, such as the Internet, a mouse input device, or a scanner. The interconnection via system bus 600 allows the central processor 606 to communicate with each subsystem and to control the execution of instructions from system memory 604 or the fixed disk 616, as well as the exchange of information between subsystems.

Specific details regarding some of the above-described aspects are provided below. The specific details of the specific aspects may be combined in any suitable manner without departing from the spirit and scope of embodiments of the invention.

Storage media and computer readable media for containing code, or portions of code, may include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, data signals, data transmissions, or any other medium which may be used to store or transmit the desired information and which may be accessed by the computer. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art may appreciate other ways and/or methods to implement the various embodiments.

It may be understood that the present invention as described above may be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art may know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software

Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, Objective C, C/C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or processing server computer.

The above description is illustrative and is not restrictive. Many variations of the invention may become apparent to those skilled in the art upon review of the disclosure. The scope of the invention may, therefore, be determined not with reference to the above description, but instead may be determined with reference to the pending claims along with their full scope or equivalents.

One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.

A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary. 

What is claimed is:
 1. A method comprising: receiving, by a merchant processing system, a token request message from a user device requesting generation of a token associated with a first identifier associated with a user account exclusive to a merchant, wherein the token request message includes the first identifier, wherein the user device is associated with a user; analyzing, by the merchant processing system, the first identifier; identifying, by the merchant processing system, that the first identifier is in a first format based on the analyzing; determining that the user account is ineligible for tokenization and provisioning on a digital wallet of the user device based on the first identifier being in the first format; identifying, by the merchant processing system, the merchant and a merchant computer of the merchant associated with the first identifier; validating, by the merchant processing system, the first identifier; receiving, by the merchant processing system, identification and verification data associated with an account holder of the user account; verifying, by the merchant processing system, an identity of the account holder using the identification and verification data, verifying including: validating, by the merchant processing system, that the account holder is the user sending the token request message; upon verifying the identity of the account holder: generating, by the merchant processing system, a universal identifier associated with the user account that is exclusive to the merchant, the universal identifier identifying the user account and the merchant processing system, wherein the universal identifier is in a second format that is eligible for tokenization and provisioning on the digital wallet of the user device, wherein the second format is attributed to the merchant processing system; transforming, by the merchant processing system, the user account from being ineligible for tokenization and provisioning to being eligible for tokenization and provisioning on the digital wallet via the universal identifier, the transforming including: transmitting, by the merchant processing system, a token request message including the universal identifier to a token issuer computer; receiving, by the merchant processing system, a token representing the universal identifier from the token issuer computer; and transmitting, by the merchant processing system, the token representing the universal identifier to the user device, wherein the token is provisioned on the digital wallet.
 2. The method of claim 1, further comprising: determining, by the merchant processing system, one or more restrictions associated with the user account; and transmitting, by the merchant processing system, the one or more restrictions to the token issuer computer, wherein the token corresponding to the universal identifier is associated with the one or more restrictions during the tokenization and provisioning.
 3. The method of claim 1, further comprising: contacting, by the merchant processing system, the merchant computer to inactivate the first identifier associated with the user account upon generation of the universal identifier.
 4. The method of claim 1, further comprising: storing, by the merchant processing system, a mapping between the universal identifier and the first identifier associated with the user account at a token vault.
 5. The method of claim 1, further comprising, prior to generating the universal identifier: determining, by the merchant processing system, that the user account is eligible for the tokenization.
 6. A merchant processing system, comprising: one or more processors; and a non-transitory computer readable storage medium communicatively coupled with the one or more processors and storing instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of: receiving a token request message from a user device requesting generation of a token associated with a first identifier associated with a user account exclusive to a merchant, wherein the token request message includes the first identifier, wherein the user device is associated with a user; analyzing the first identifier; identifying that the first identifier is in a first format based on the analyzing: determining that the user account is ineligible for tokenization and provisioning on a digital wallet of the user device based on the first identifier being in the first format; identifying the merchant and a merchant computer of the merchant associated with the first identifier; validating the first identifier; receiving identification and verification data associated with an account holder of the user account; verifying an identity of the account holder using the identification and verification data, verifying including: validating that the account holder is the user sending the token request message; upon verifying the identity of the account holder; generating a universal identifier associated with the user account that is exclusive to the merchant, the universal identifier identifying the user account and the merchant processing system, wherein the universal identifier is in a second format that is eligible for tokenization and provisioning on the digital wallet of the user device, wherein the second format is attributed to the merchant processing system; transforming the user account from being ineligible for tokenization and provisioning to being eligible for tokenization and provisioning on the digital wallet via the universal identifier, the transforming including: transmitting a token request message including the universal identifier to a token issuer computer; receiving a token representing the universal account identifier from the token issuer computer; and transmit the token representing the universal identifier to the user device, wherein the token is provisioned on the digital wallet.
 7. The merchant processing system of claim 6, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to perform the steps of: determining one or more restrictions associated with the user account; and transmitting the one or more restrictions to the token issuer computer, wherein the token corresponding to the universal identifier is associated with the one or more restrictions during the tokenization and provisioning.
 8. The merchant processing system of claim 6, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to perform the steps of: storing a mapping between the universal identifier and the first identifier associated with the user account at a token vault.
 9. The merchant processing system of claim 6, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to perform the step of, prior to generating the universal identifier: determining that the user account is eligible for the tokenization.
 10. The merchant processing system of claim 6, wherein the instructions, when executed by the one or more processors, further cause the one or more processors to perform the step of: contacting the merchant computer to inactivate the first identifier associated with the user account upon generation of the universal identifier. 